Update README.md #176
Closed
Update README.md #176
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
NzSN
pushed a commit
to NzSN/chromium
that referenced
this pull request
Jun 20, 2023
Change-Id: Id9cb7b004f39344dd4b984e33e1f1a2f5dd16759 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4499768 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5735@{chromium#176} Cr-Branched-From: 2f562e4-refs/heads/main@{#1135570}
msizanoen1
pushed a commit
to qtmlabs/chromium
that referenced
this pull request
Jun 29, 2023
(cherry picked from commit 513ca72) Bug: 1458347, b:288975117 Change-Id: I17521e07939f099d717a808dbe36658c9e94e67b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4648359 Reviewed-by: Theodore Olsauskas-Warren <sauski@google.com> Commit-Queue: Mariam Ali <alimariam@google.com> Cr-Original-Commit-Position: refs/heads/main@{#1162972} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4650791 Auto-Submit: Mariam Ali <alimariam@google.com> Commit-Queue: Theodore Olsauskas-Warren <sauski@google.com> Cr-Commit-Position: refs/branch-heads/5845@{chromium#176} Cr-Branched-From: 5a5dff6-refs/heads/main@{#1160321}
msizanoen1
pushed a commit
to qtmlabs/chromium
that referenced
this pull request
Jun 30, 2023
…r + CTA" This reverts commit 115b260. Reason for revert: Desired strings have changed. Original change's description: > [Merge M116] Privacy Sandbox: Update Topics EEA consent header + CTA > > (cherry picked from commit 513ca72) > > Bug: 1458347, b:288975117 > Change-Id: I17521e07939f099d717a808dbe36658c9e94e67b > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4648359 > Reviewed-by: Theodore Olsauskas-Warren <sauski@google.com> > Commit-Queue: Mariam Ali <alimariam@google.com> > Cr-Original-Commit-Position: refs/heads/main@{#1162972} > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4650791 > Auto-Submit: Mariam Ali <alimariam@google.com> > Commit-Queue: Theodore Olsauskas-Warren <sauski@google.com> > Cr-Commit-Position: refs/branch-heads/5845@{chromium#176} > Cr-Branched-From: 5a5dff6-refs/heads/main@{#1160321} Bug: 1458347, b:288975117 Change-Id: I8f5f200c8b7d7939a258051502a8f2b6cabc5790 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4650763 Commit-Queue: Krishna Govind <govind@chromium.org> Owners-Override: Krishna Govind <govind@chromium.org> Reviewed-by: Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/branch-heads/5845@{chromium#219} Cr-Branched-From: 5a5dff6-refs/heads/main@{#1160321}
aetota61
pushed a commit
to monkbrowser/monk-browser
that referenced
this pull request
Aug 2, 2023
Roll Chrome Linux PGO profile from chrome-linux-5790-1685490441-c10ba259e9cd03db48de1e56bf3f8f27a54ca699.profdata to chrome-linux-5790-1685509565-64c88fead0ed0a15f7a24b1be9c887b7897e96c4.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-linux-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m115.try:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ie7b4c48949ff15032f9a1614bf2849f87d76f9ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4575729 Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5790@{chromium#176} Cr-Branched-From: 1d71a33-refs/heads/main@{#1148114}
trflynn89
pushed a commit
to RebelBrowser/rebel
that referenced
this pull request
Oct 26, 2023
…118.0.5993.9-r1 to 118-5978.0-1693821895-benchmark-118.0.5993.10-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-atom-chromium-beta Please CC c-compiler-chrome@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: Ia83c1186f029d4b460f38c787b4bc48e732452dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4856731 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5993@{chromium#176} Cr-Branched-From: 5113507-refs/heads/main@{#1192594}
vuzix-jeff
pushed a commit
to Vuzix/chromium
that referenced
this pull request
Nov 3, 2023
…ecation trial This CL removes the failure expectation from the wpt_internal web-locks WPTs and ensures that third-party contexts are unpartitioned under a top-level site that receives the `DisableThirdPartyStoragePartitioning` deprecation trial token. This CL also changes the format of token delivery from headers (no longer supported by this deprecation trial) to <meta> tags. (cherry picked from commit e7e10e3) Fixed: 1420973 Change-Id: I0530e5861b57b984a55dd42934f8ef6322dc24fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4300229 Reviewed-by: Ari Chivukula <arichiv@chromium.org> Commit-Queue: Kyra Seevers <kyraseevers@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1112257} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4304190 Cr-Commit-Position: refs/branch-heads/5615@{chromium#176} Cr-Branched-From: 9c6408e-refs/heads/main@{#1109224}
vuzix-jeff
pushed a commit
to Vuzix/chromium
that referenced
this pull request
Nov 3, 2023
Roll Chrome Win32 PGO profile from chrome-win32-6045-1696736910-7556dabf25e72548199bd2a3d4a5453f9bd4961f.profdata to chrome-win32-6045-1696757941-65edb03d02bc3ac87df3936736bd7646ade1bc75.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m119.try:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I59825c90455de121ee7acf8845047bf2caddd120 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4920921 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6045@{chromium#176} Cr-Branched-From: 905e8bd-refs/heads/main@{#1204232}
Aikoyori
pushed a commit
to Pissandshittium/pissandshittium
that referenced
this pull request
Dec 8, 2023
Roll Chrome Win32 PGO profile from chrome-win32-6099-1699095171-9376c82fd96ad0b151cab7b4463a9365038304b9.profdata to chrome-win32-6099-1699119607-63f745ac492724eb2ef2db8693809863a04745ee.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I7796a404254f310e963810dfd424d6b1ffbd0c7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5006202 Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{chromium#176} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
aarongable
pushed a commit
that referenced
this pull request
Jan 6, 2024
Roll Chrome Win64 PGO profile from chrome-win64-6167-1702141771-55baffeaafc705ddb17fa950d786ebfdbb51f1d0.profdata to chrome-win64-6167-1702156039-eb5f8d1ad7fcda6910c9b18b4200613971a14bc8.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m121.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: If03c7afee2a2d9839a72b3b08d371fd356dab71b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5108238 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6167@{#176} Cr-Branched-From: 222e786-refs/heads/main@{#1233107}
aarongable
pushed a commit
that referenced
this pull request
Jan 27, 2024
Roll Chrome Linux PGO profile from chrome-linux-6261-1706311063-857457267535ecb74afb732917c777ac14662cb9.profdata to chrome-linux-6261-1706326559-307e9256be53de7e8890c7b32c2171f025a42bae.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-linux-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m122.try:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: If07709fae51be83bbd418dbb931f0a32cd9c3a44 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5242287 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6261@{#176} Cr-Branched-From: 9755d9d-refs/heads/main@{#1250580}
ecotopian
pushed a commit
to ecosia/chromium-android-browser
that referenced
this pull request
Feb 12, 2024
…11.0.5563.13-r1 to 111-5550.0-1675078804-benchmark-111.0.5563.14-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-arm-chromium-beta Please CC c-compiler-chrome@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: I666c7cfb16a87f163cb918c06a14fe7d7ef685e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4223278 Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5563@{chromium#176} Cr-Branched-From: 3ac59a6-refs/heads/main@{#1097615}
aarongable
pushed a commit
that referenced
this pull request
Feb 26, 2024
This CL implements the `SessionAuthzReauthorizer`, which is created by the `SessionAuthzAuthenticator` and hooked up to the `JingleSession`. It periodically talks to the SessionAuthz server for session reauth, with some retry logic, and it closes the session if reauthorization fails. (cherry picked from commit 21cc4f1) Bug: 325688267, b/323068262 Change-Id: If2a92c76b7cf7cdbe02ed00b4f513408dd3e3325 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5302327 Reviewed-by: Joe Downing <joedow@chromium.org> Auto-Submit: Yuwei Huang <yuweih@chromium.org> Commit-Queue: Joe Downing <joedow@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1264553} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5324925 Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6312@{#176} Cr-Branched-From: 6711dcd-refs/heads/main@{#1262506}
aarongable
pushed a commit
that referenced
this pull request
Mar 24, 2024
Automatic update for 2024-03-24 UTC Change-Id: Ica6b79895e76ca1e78daafc7a8b44830876c96d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5390604 Commit-Queue: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com> Bot-Commit: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com> Cr-Commit-Position: refs/branch-heads/6367@{#176} Cr-Branched-From: d158c6d-refs/heads/main@{#1274542}
aarongable
pushed a commit
that referenced
this pull request
Apr 21, 2024
Roll Chrome Linux PGO profile from chrome-linux-6422-1713629309-777fcfb8d4e2a0cf8cf24568d1854ad6683a2272-b1b5087e8ab56de55bd40d6a50f29d1c847c2872.profdata to chrome-linux-6422-1713652726-2c75e69e0ddf977cddce2fec9bdd765eb7d08d92-2fdcfa53d4f6c175cb0296fa40a6058659e40db8.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-linux-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I00ad3b2d4c421d38f8e05e7e45d9cc6d5ac71cd5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5468938 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6422@{#176} Cr-Branched-From: 9012208-refs/heads/main@{#1287751}
aarongable
pushed a commit
that referenced
this pull request
May 17, 2024
Roll Chrome Win64 PGO profile from chrome-win64-6478-1715944004-d57daca6486dfbae9e7a1630794b1b5052aebb96-582cd3edc39dd59a36d814d4675db522ecf4ccf7.profdata to chrome-win64-6478-1715968334-1fd35c6bf75058e4fdf5c0f07f86369e2fc0222c-80f4d847291cb182187df3b25ce3d13c699b4837.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m126.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I103b129877c821a99fe8fea46ad93991b28e17bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5548620 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6478@{#176} Cr-Branched-From: e6143ac-refs/heads/main@{#1300313}
consp1racy
pushed a commit
to signageos/chromium-chromium
that referenced
this pull request
May 18, 2024
…rnals UI What: Adds a chrome://private-aggregation-internals page which supports: * showing pending and sent aggregatable reports stored by the aggregation service * sending selected reports from the web UI * clearing data Screenshot can be found in crbug.com/1348029. This change re-uses the table approach used by chrome://attribution-reporting-internals. (cherry picked from commit 35c275f) Bug: 1348029 Change-Id: I23ac2a037c1d2d453f3bf1fd719caf0f92b2fac8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3789670 Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Alex Turner <alexmt@chromium.org> Reviewed-by: Samuel Huang <huangs@chromium.org> Reviewed-by: Alex Gough <ajgo@chromium.org> Commit-Queue: John Delaney <johnidel@chromium.org> Reviewed-by: John Lee <johntlee@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1037228} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3857103 Reviewed-by: Robert Sesek <rsesek@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5249@{chromium#176} Cr-Branched-From: 4f7bea5-refs/heads/main@{#1036826}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.